PEPFAR's annual planning process is done either at the country (COP) or regional level (ROP).
PEPFAR's programs are implemented through implementing partners who apply for funding based on PEPFAR's published Requests for Applications.
Since 2010, PEPFAR COPs have grouped implementing partners according to an organizational type. We have retroactively applied these classifications to earlier years in the database as well.
Also called "Strategic Areas", these are general areas of HIV programming. Each program area has several corresponding budget codes.
Specific areas of HIV programming. Budget Codes are the lowest level of spending data available.
Expenditure Program Areas track general areas of PEPFAR expenditure.
Expenditure Sub-Program Areas track more specific PEPFAR expenditures.
Object classes provide highly specific ways that implementing partners are spending PEPFAR funds on programming.
Cross-cutting attributions are areas of PEPFAR programming that contribute across several program areas. They contain limited indicative information related to aspects such as human resources, health infrastructure, or key populations programming. However, they represent only a small proportion of the total funds that PEPFAR allocates through the COP process. Additionally, they have changed significantly over the years. As such, analysis and interpretation of these data should be approached carefully. Learn more
Beneficiary Expenditure data identify how PEPFAR programming is targeted at reaching different populations.
Sub-Beneficiary Expenditure data highlight more specific populations targeted for HIV prevention and treatment interventions.
PEPFAR sets targets using the Monitoring, Evaluation, and Reporting (MER) System - documentation for which can be found on PEPFAR's website at https://www.pepfar.gov/reports/guidance/. As with most data on this website, the targets here have been extracted from the COP documents. Targets are for the fiscal year following each COP year, such that selecting 2016 will access targets for FY2017. This feature is currently experimental and should be used for exploratory purposes only at present.
Years of mechanism: 2011 2012 2013 2014 2015 2016
NOTE: The following is taken from summaries released by PEPFAR on the PEPFAR Data Dashboard. They are incomplete summary paragraphs only and do not contain the full mechanism details. When the full narratives are released, we will update the mechanism pages accordingly.
The objectives of post are to: 1) support community driven projects targeting KPs that address prevention, HTC, access to treatment & care, empowerment of persons infected/affected, and S&D; and 2) Build capacity of organizations and systems contributing to the National HIV response. These objectives are also closely related to the CRSF objectives of "Reducing vulnerability to sexual transmission of HIV"; "Establishing comprehensive, gender sensitive and targeted prevention programs"; and "Partner with communities to strengthen individuals who provide comprehensive and integrated HIV services". Cost efficiencies for this mechanism will be realized through increasing collaboration with other USG agencies, the National Program and NGOs. The mechanism will transition to the GOJ and local organizations as a result of the focus on capacity building and knowledge transfer. All activities funded by this mechanism will be reported by PCVs and monitored and evaluated by post and HQ. This Mechanism has shown an increase in outlays as a result of improved accuracy in allocating costs and increased utilization of small grants by PCVs to fund community-led projects.
Since COP2014, PEPFAR no longer produces narratives for every mechanism it funds. However, PEPFAR has now included performance targets or indicator information for each mechanism based on the Monitoring, Evaluation, and Reporting (MER) system. The MER guidance is available on PEPFAR's website https://www.pepfar.gov/reports/guidance/. Note that COP years 2014-2015 were under a previous version of the MER system and the indicators and definitions may have changed as of the new 2.0 guidance.
